Reviewing files that changed from the base of the PR and between 6989cbc and 34ce3e8.

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

• components/line_messaging_api/actions/send-broadcast-message/send-broadcast-message.mjs (1 hunks)
• components/line_messaging_api/actions/send-multicast-message/send-multicast-message.mjs (1 hunks)
• components/line_messaging_api/actions/send-push-message/send-push-message.mjs (1 hunks)
• components/line_messaging_api/actions/send-reply-message/send-reply-message.mjs (1 hunks)
• components/line_messaging_api/line_messaging_api.app.mjs (1 hunks)
• components/line_messaging_api/package.json (2 hunks)
• components/line_messaging_api/sources/common/base-webhook.mjs (1 hunks)
• components/line_messaging_api/sources/new-message-received/new-message-received.mjs (1 hunks)
• components/line_messaging_api/sources/new-message-received/test-event.mjs (1 hunks)

• GitHub Check: Publish TypeScript components
• GitHub Check: Verify TypeScript components
• GitHub Check: Lint Code Base
• GitHub Check: pnpm publish

components/line_messaging_api/package.json (2)

3-3: Version bump looks good

Package version update to 0.1.0 aligns with introducing new public surface (app wrappers, actions, source).

---

15-17: Dependency addition is appropriate and compliant with org learnings

Adding "@pipedream/platform" is required for axios usage in the app. Also, thanks for not adding built-in Node modules as dependencies—this follows our learning on avoiding native modules in package.json.

components/line_messaging_api/sources/new-message-received/test-event.mjs (1)

1-19: Sample event LGTM

Shape matches a LINE message event and is suitable for sampleEmit. Values appear non-sensitive.

components/line_messaging_api/line_messaging_api.app.mjs (3)

35-75: Endpoint wrappers map correctly to LINE Messaging API

createWebhook/getWebhook and message send (push/reply/multicast/broadcast) routes look correct and consistent.

---

24-33: Require valid step context ($) and set JSON content-type in requests

Defaulting $ = this may mask missing or invalid step contexts and lead to runtime errors in the Pipedream axios client. Enforce $ as a required parameter and explicitly set the JSON content‐type header for all requests.

Suggested diff:

-  _makeRequest({
-    $ = this, path, ...opts
-  }) {
-    return axios($, {
+  _makeRequest({ $, path, ...opts }) {
+    if (!$) {
+      throw new Error("Missing step context ($). Pass {$} when calling app methods.");
+    }
+    return axios($, {
       url: `${this._baseUrl()}${path}`,
       headers: {
         Authorization: `Bearer ${this.$auth.long_lived_channel_access_token}`,
+        "Content-Type": "application/json",
       },
       ...opts,
     });

• I ran the provided grep commands to confirm all callers pass {$}, but they returned no matches under components/line_messaging_api/.
• Please manually verify that every invocation of your app methods (e.g. sendPushMessage, replyMessage, getWebhook, etc.) includes the step context object { $ }.

---

29-31: Confirm auth token key matches the app auth schema
The _makeRequest method uses this.$auth.long_lived_channel_access_token for the Authorization header, but this file doesn’t define any auth props. Please verify that your app’s auth configuration declares a secret named long_lived_channel_access_token (not, for example, channel_access_token), or update the code to use the correct $auth field—otherwise API calls will fail with 401 Unauthorized.

components/line_messaging_api/actions/send-push-message/send-push-message.mjs (1)

29-45: Run logic LGTM

Payload structure and wrapper usage are correct; summary is helpful.

components/line_messaging_api/actions/send-broadcast-message/send-broadcast-message.mjs (3)

1-8: LGTM!

The import path and action structure follow standard Pipedream patterns correctly.

---

9-23: LGTM!

Props structure is consistent with other LINE messaging actions and correctly uses propDefinitions for shared properties.

---

24-40: LGTM!

The run function implementation correctly follows the LINE API structure and is consistent with other messaging actions in the PR. The nullish coalescing operator usage and summary export are appropriate.

components/line_messaging_api/actions/send-reply-message/send-reply-message.mjs (3)

1-8: LGTM!

Import and action structure are consistent with other LINE messaging actions.

---

9-28: LGTM!

Props structure correctly adds the reply-specific replyToken prop while reusing shared propDefinitions for common properties.

---

29-46: LGTM!

The run function correctly implements the reply message pattern with the required replyToken field and provides a helpful summary message.

components/line_messaging_api/sources/common/base-webhook.mjs (2)

1-8: LGTM!

Import statements and base structure are appropriate for a webhook base class.

---

9-26: LGTM!

The activate hook implementation correctly sets up the webhook with appropriate error handling and user guidance. The sequence of operations and error messaging provide good developer experience.

components/line_messaging_api/sources/new-message-received/new-message-received.mjs (3)

1-11: LGTM!

Import statements and source structure correctly extend the base webhook with appropriate metadata.

---

22-32: LGTM!

The run function correctly handles LINE webhook events with proper filtering and emission. The early return and event type filtering are appropriate defensive programming practices.

---

33-34: LGTM!

Sample emit usage follows standard Pipedream patterns.